Res2Net and Res2NeXt, again #195
Merged
+278
−57
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
darsnack
requested changes
Aug 10, 2022
Also misc. cleanup Co-Authored-By: Kyle Daruwalla <[email protected]>
|
Need to update the symbols in the |
Also fix `tuplify`
2 tasks
darsnack
approved these changes
Aug 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is an implementation for Res2Net and Res2NeXt, yet again. It closes #181 and closes #123 (supersedes) since those are now outdated, and makes use of the newest APIs merged in #174 and #190. More comprehensive docs for another PR in the revamp, perhaps, but this gets the models in with all possible configuration options